home *** CD-ROM | disk | FTP | other *** search
- Path: swidir.switch.ch!epflnews!not-for-mail
- From: "Stefan Monnier" <stefan.monnier@lia.di.epfl.ch>
- Newsgroups: comp.lang.lisp,comp.lang.c++
- Subject: Re: Why garbage collection?
- Date: 2 Feb 1996 10:58:37 GMT
- Organization: Ecole Polytechnique Federale de Lausanne
- Message-ID: <4esqot$pcm@info.epfl.ch>
- References: <rvillDL4v3n.I8r@netcom.com> <4ecmfo$as9@news2.ios.com> <4ei4og$la1@info.epfl.ch> <4eqh80$c9f@news2.ios.com>
- NNTP-Posting-Host: liasg9.epfl.ch
- Originator: monnier@lia.di.epfl.ch (Stefan Monnier)
-
- In article <4eqh80$c9f@news2.ios.com>,
- Vlastimil Adamovsky <vlad@gramercy.ios.com> wrote:
- ] Why would you need to modify the vtable. Create a pointer to your
- ] table and modify it as you wish. By the way, can you modify C -
-
- But then you have the vtable pointer plus your table pointer:
- I call that a waste.
- You don't have enough access to the representation to take advantage of it.
- This is what I call "too high-level".
- The "too low-level" stuff is the fact that casts are too powerful to enable the
- creation of a copying GC unless you severely restrict the set of programs
- correctly handled.
-
- There are probably other examples of "too high" or "too low" levels in C++
- (implicit calls to constructors is probably among the former)
-
-
- Stefan
-